Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.77%. Comparing base (ef55c27) to head (482226b).

✅ All tests successful. No failed tests found.

@@             Coverage Diff             @@
##           develop    #4177      +/-   ##
===========================================
+ Coverage    78.73%   78.77%   +0.03%     
===========================================
  Files          830      830              
  Lines        75512    75536      +24     
===========================================
+ Hits         59457    59501      +44     
+ Misses       16055    16035      -20     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

I honestly believe this is the wrong solution, we shouldn't rely on exiting a room for it to be marked properly. What if they background the app and it just dies in the background, your state will still be wrong. So sure, this works sometimes but not enough.

Do you know why reaching the bottom of the timeline doesn't do the right thing?

Am I right in believing that the unread marker should behave similarly to the read receipts, marking the top of the currently read content until the bottom is reached and then become unset? We don't have an api for that, do we?

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud